Method and apparatus for authorized login

ABSTRACT

Techniques for processing user logins are described. One example method includes receiving a first user input to zoom out a first application, wherein the first application is displayed on a first area of a screen of a device; zooming out the first application to be displayed on a second area of the screen; and displaying an icon of a second application on a third area of the screen, wherein a user has logged into the second application on the device; receiving a second user input to drag the displayed icon of the second application from the third area to the second area; transmitting login authorization information of the second application to the first application; and submitting, by the first application, the login authorization information to a server of the second application through a server of the first application; and authorizing logging into the first application on the device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of PCT Application No.PCT/CN2017/113555, filed on Nov. 29, 2017, which claims priority toChinese Patent Application No. 201611124494.X, filed on Dec. 8, 2016,and each application is hereby incorporated by reference in itsentirety.

TECHNICAL FIELD

The present application relates to the field of computer applications,and in particular, to a method and an apparatus for an authorized login.

BACKGROUND

An authorized login is a quick login mode that a user is authorized todirectly log in to an application by using a login identity of anotherapplication that the user has successfully logged in to. However, inpractice, when a user browses an application, if an authorized loginneeds to be performed to the current application by using a loginidentity of another application that the user has successfully logged into, the user usually needs to perform a plurality of operations on alogin page of the application to complete the login. Therefore, theinteraction is relatively complex and is not convenient.

SUMMARY

The present application provides a method for an authorized login, wherethe method includes the following: zooming out a user interface of afirst application in response to a zooming operation for the userinterface of the first application; displaying an icon of at least onesecond application that a user has logged in to in a blank areagenerated after the user interface of the first application is zoomedout, where the first application pre-establishes an association with thesecond application; transmitting login authorization information of thesecond application to the first application in response to an operationof dragging the icon of the second application from the blank area tothe zoomed-out user interface of the first application, so that thefirst application submits the login authorization information of thesecond application to a server of the second application by using aserver of the first application for login authorization verification;and performing an authorized login to the first application in responseto a notification message that is returned by the server of the secondapplication through the server of the first application, where thenotification message indicates that the login authorization informationis verified.

The present application further provides an apparatus for an authorizedlogin, where the apparatus includes the following: a zooming module,configured to zoom out a user interface of a first application inresponse to a zooming operation for the user interface of the firstapplication; a display module, configured to display an icon of at leastone second application that a user has logged in to in a blank areagenerated after the user interface of the first application is zoomedout, where the first application pre-establishes an association with thesecond application; a transmission module, configured to transmit loginauthorization information of the second application to the firstapplication in response to an operation of dragging the icon of thesecond application from the blank area to the zoomed-out user interfaceof the first application, so that the first application submits thelogin authorization information of the second application to a server ofthe second application by using a server of the first application forlogin authorization verification; and a login module, configured toperform an authorized login to the first application in response to anotification message that is returned by the server of the secondapplication through the server of the first application, where thenotification message indicates that the login authorization informationis verified.

In the present application, an interaction method that can be used toquickly complete an authorized login is provided. A user can perform apredetermined zooming operation on a user interface of a firstapplication to trigger an operating system of a terminal device to zoomout the user interface of the first application. An icon of at least onesecond application that establishes an association with the firstapplication and that the user has logged in to is displayed in a blankarea generated after the user interface of the first application iszoomed out. Then the user drags the icon of the second application tothe user interface of the first application to trigger the terminaldevice to transmit login authorization information of the secondapplication to the first application, and the first application submitsthe login authorization information of the second application to aserver of the second application by using a server of the firstapplication for login authorization verification. After the verificationsucceeds, the user can log in to the second application by using thelogin authorization information of the first application. As such, theuser can quickly complete the authorized login by using a simple andquick interacting operation, to reduce the operation complexity inperforming the authorized login and improve user's interactiveexperience.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram illustrating interaction of performing anauthorized login in a related technology, according to the presentapplication;

FIG. 2 is a flowchart illustrating a method for an authorized login,according to an implementation of the present application;

FIG. 3 is a schematic diagram illustrating interaction of zooming out auser interface, according to an implementation of the presentapplication;

FIG. 4 is a schematic diagram illustrating interaction of displaying anicon of an associated application in a blank area of a zoomed-out userinterface, according to an implementation of the present application;

FIG. 5 is a schematic diagram illustrating interaction of an authorizedlogin, according to an implementation of the present application;

FIG. 6 is a schematic diagram illustrating interaction of transmitting atarget object between applications in an authorized login scenario,according to an implementation of the present application;

FIG. 7 is a logical block diagram illustrating an apparatus for anauthorized login, according to an implementation of the presentapplication;

FIG. 8 is a structural diagram illustrating hardware of a terminaldevice that includes the apparatus for an authorized login, according toan implementation of the present application; and

FIG. 9 is a flowchart illustrating an example of a computer-implementedmethod for performing an authorized login, according to animplementation of the present disclosure.

DESCRIPTION OF IMPLEMENTATIONS

In a related technology, when a user performs an authorized login to acurrently browsed application by using a login identity of a third-partyapplication that the user has successfully logged in to, the userusually needs to perform a plurality of operations on a login page ofthe application to complete the login. Therefore, the interaction isrelatively complex and is not convenient.

For example, referring to FIG. 1, the application is an APP applicationof a mobile terminal. Usually, login entries that correspond to aplurality of third-party APPs can be set in a login interface of currentAPP 1. When the user needs to log in to APP 1 by using a login identityof third-party APP 2 that the user has successfully logged in to, theuser can trigger a login entry that corresponds to APP 2 to jump to alogin authorization page of APP 2, and further perform an interactingoperation in the login authorization page. After confirming an operationof this authorized login, APP 1 can initiate login authorizationverification to a server that corresponds to APP 2, to complete theauthorized login to APP 1 by using the login identity of APP 2.

It can be seen that, in the related technology, if the user needs toperform an authorized login to the currently browsed application byusing the login identity of the third-party application, the user needsto perform at least two operations: triggering the authorized login, andconfirming the authorized login after a page jump, to complete theauthorized login operation. Therefore, the interaction is relativelycomplex and is not convenient.

To alleviate the previous problem, an interaction method that can beused to quickly complete an authorized login is provided. A user canperform a predetermined zooming operation on a user interface of a firstapplication to trigger an operating system of a terminal device to zoomout the user interface of the first application. An icon of at least onesecond application that establishes an association with the firstapplication and that the user has logged in to is displayed in a blankarea generated after the user interface of the first application iszoomed out. Then the user drags the icon of the second application tothe user interface of the first application to trigger the terminaldevice to transmit login authorization information of the secondapplication to the first application, and the first application submitsthe login authorization information of the second application to aserver of the second application by using a server of the firstapplication for login authorization verification. After the verificationsucceeds, the user can log in to the second application by using thelogin authorization information of the first application. As such, theuser can quickly complete the authorized login by using a simple andquick interacting operation, to reduce the operation complexity inperforming the authorized login and improve user's interactiveexperience.

The following describes the present application by using implementationswith reference to application scenarios.

FIG. 2 shows a method for an authorized login, according to animplementation of the present application. The method is applied to anoperating system of a terminal device, and the method includes thefollowing steps.

Step 201: Zoom out a user interface of a first application in responseto a zooming operation for the user interface of the first application.

Step 202: Display an icon of at least one second application that a userhas logged in to in a blank area generated after the user interface ofthe first application is zoomed out, where the first applicationpre-establishes an association with the second application.

The terminal device can be a mobile terminal device, or can be a PCterminal device. For example, the terminal device can be a touchscreensmartphone, or can be a notebook computer or a tablet computer. Theoperating system of the terminal device can be IOS, ANDROID, WINDOWS, oranother type of operating system.

The first application is an application that the user can be authorizedto directly log in to by using a login identity of another third-partyapplication. The second application is an application that the user hassuccessfully logged in to and can provide an associated authorized loginservice for another application.

For example, in practice, the first application can be minorityapplications that have a relatively small number of users and have somecharacteristic functions. The second application can be applicationsthat have a large number of users and can provide an associatedauthorized login service for other minority applications, for example,applications such as ALIPAY and WeChat.

In practice, the first application and the second application can be APPapplications installed on the mobile terminal device, or can be Webapplications installed on the PC terminal device. Implementations arenot limited in the present example.

In an initial state, a server that corresponds to the first applicationand a server that corresponds to the second application can separatelyestablish an association between the first application and the secondapplication. The association can be a login association between thefirst application and the second application. After the loginassociation between the first application and the second application isestablished on their respective servers of the first application and thesecond application, the servers that correspond to the first applicationand the second application provide the function permission to directlycomplete a login by using a login identity of each other.

In the present example, in a process that the user browses the firstapplication, if the user needs to log in to the first application byusing a login identity of a second application that the user hassuccessfully logged in to and that is installed on the terminal device,the user can perform a predetermined zooming operation on the userinterface of the first application to trigger the operating system ofthe terminal device (which is briefly referred to as the operatingsystem below) to zoom out the user interface. After detecting thezooming operation, the operating system can zoom out the user interfacebased on a predetermined zooming-out percentage in response to thezooming operation.

The predetermined zooming operation can include a two-finger pinchgesture for the user interface, a predetermined trigger operation (suchas a double-click operation or another type of operation) for the userinterface, and a predetermined trigger operation for a predeterminedvirtual button (such as a zooming button) or an physical button (such asa fingerprint button or another physical button on the terminal device).

For example, referring to FIG. 3, when the terminal device is atouchscreen device, the user can perform a two-finger pinch gestureshown in FIG. 3 on a currently displayed user interface of the firstapplication to trigger the operating system to zoom out the userinterface.

When the terminal device is a non-touchscreen device, in a case, azooming button can be set in a currently displayed user interface of thefirst application, and the user can double click the zooming button totrigger the operating system to zoom out the user interface; or inanother case, an event of zooming out the user interface can bepredefined in the operating system as a trigger event of performing adouble-click operation on a fingerprint button of the terminal device,and the operating system can zoom out the user interface in response tothe double-click operation when detecting the double-click operationperformed by the user on the fingerprint button.

In the present example, after zooming out the user interface based onthe predetermined percentage in response to the zoom operation performedby the user on the user interface of the first application, theoperating system can display icons of a plurality of second applicationsthat pre-establish an association with the first application in theblank area generated after the user interface is zoomed out.

A size of the blank area can be adjusted synchronously by adjusting thezooming percentage. The number of icons of second applications displayedin the blank area can also be customized based on the number of secondapplications that actually establish an association with the firstapplication.

For example, referring to FIG. 4, assume that the first application isAPP 1, and the second application includes APP 2, APP 3, and APP 4. Whenthe user performs a predetermined zooming operation on a user interfaceof APP 1 to trigger the operating system to zoom out the user interfacebased on a predetermined percentage, APP 2, APP 3, and APP 4 can bedisplayed at any location in a blank area generated after the userinterface of APP 1 is zoomed out (FIG. 4 shows a blank area displayedabove the zoomed-out user interface).

Step 203: Transmit login authorization information of the secondapplication to the first application in response to an operation ofdragging the icon of the second application from the blank area to thezoomed-out user interface of the first application, so that the firstapplication submits the login authorization information of the secondapplication to a server of the second application by using a server ofthe first application for login authorization verification.

Step 204: Perform an authorized login to the first application inresponse to a notification message that is returned by the server of thesecond application through the server of the first application, wherethe notification message indicates that the login authorizationinformation is verified.

In the present example, after the operating system displays the icons ofthe plurality of second applications that establish an association withthe first application in the blank area generated after the userinterface of the first application is zoomed out, the user can directlydrag the icon of the second application displayed in the control area toan area where the zoomed-out user interface of the first application islocated, to trigger the operating system to transmit the loginauthorization information of the dragged second application to the firstapplication.

The login authorization information can include an applicationidentifier (such as an APP ID) of the second application, a useridentifier (such as a UID) allocated by the server of the secondapplication to the user after the user successfully logs in to thesecond application, and a login certificate (such as a tokencertificate) sent by the server of the second application after the usersuccessfully logs in to the second application.

For example, in practice, after the user successfully logs in to anapplication by entering a login account and a password, a server of theapplication usually allocates a corresponding UID to the user, and sendsa corresponding token certificate to the application. The UID is used touniquely identify an identity of the user. The token certificate usuallyis a random string calculated based on a predetermined token algorithm,and is used to verify the login identity of the user. In this case, thelogin authorization information can include the application identifierof the second application, the UID allocated to the user after the usersuccessfully logs in to the second application, and the tokencertificate.

In the present example, an open interface (API) can be preconfigured inthe second application to implement data communication between the firstapplication and the second application, and the open interface is usedto transmit data between applications.

When detecting an operation of dragging, by the user, an icon of anysecond application displayed in the blank area to the zoomed-out userinterface of the first application, the operating system can invoke theopen interface preconfigured in the second application, then use loginauthorization information used by the user to log in to the secondapplication as an invocation parameter, and transmit the invocationparameter to the second application.

In the present example, after the user successfully transmits the loginauthorization information of the second application to the firstapplication by dragging the icon of any second application in the blankarea, the first application can interact with the server of the firstapplication based on a connection pre-established between the firstapplication and the server of the first application, to submit the loginauthorization information of the second application to the server of thefirst application.

After receiving the login authorization information of the secondapplication, the server of the first application can continue to submitthe login authorization information of the second application to theserver of the second application for login authorization verification byusing a data transmission invoking mechanism between the servers becausea login association is also pre-established between the server of thefirst application and the server of the second application.

After the login authorization information transmitted by the server ofthe first application is verified, the server of the second applicationcan return a notification message of “verification succeeds” to theserver of the first application. After receiving the notificationmessage, the server of the first application can set the firstapplication to a login state by using personal information (such as theuser's UID and personal data) used when the user logs in to the secondapplication, and then continue to send the notification message to theoperating system. Similarly, after receiving the notification message,the operating system can also invoke, at a system level, the personalinformation used when the user logs in to the second application, toautomatically log in to the first application.

For example, referring to FIG. 5, assume that the first application isAPP 1, the second application includes APP 2, APP 3, and APP 4, andicons of APP 2, APP 3, and APP 4 are displayed in a blank area generatedafter a user interface of APP 1 is zoomed out. Assume that the userneeds to perform an authorized login to APP 1 by using a login identityof APP 2. In this case, the user can drag the icon of APP 2 to thezoomed-out user interface of APP 1. After detecting an operation ofdragging the icon of APP 2 to the zoomed-out user interface of APP 1,the operating system can invoke the open interface preconfigured in APP1, use an APP ID of APP 2, a UID allocated by a server of APP 2 to theuser, and a token certificate sent by the server of APP 2 as invocationparameters, and transmit the invocation parameters to APP 1 by using theopen interface. Then APP 1 can continue to submit, to the server of APP2 by using a server of APP 1 for verification, the APP ID of APP 2, theUID allocated by the server of APP 2 to the user, and the tokencertificate sent by the server of APP 2. When confirming throughverification that the token certificate is valid, the server of APP 2can return a notification message of “verification succeeds” to theserver of APP 1. Then the server of APP 1 can fetch personal informationreserved by the user on the server of APP 2 to complete the loginauthorization, and send the notification message to the operatingsystem. After receiving the notification message, the operating systemcan also fetch the personal information used by the user to log in toAPP 2 to automatically log in to APP 1.

Certainly, after the operating system invokes the personal informationused when the user logs in to the second application to automaticallylog in to the first application for completing the authorized login, theoperating system can further restore the user interface of the firstapplication to a default size.

It can be seen that, in this method, a user can drag an icon of athird-party application displayed in a blank area in a zoomed-out userinterface of a current application to the user interface of the currentapplication, so that a login authorization operation can be quicklyperformed on the current application by using a login identity of thethird-party application. Therefore, the operation complexity inperforming an authorized login can be reduced, and user's interactiveexperience can be improved.

In the present example, after the operating system zooms out the userinterface of the first application in response to the zooming operationperformed by the user on the user interface of the first application,and displays the icons of the plurality of second applications thatpre-establish a login association with the first application in theblank area generated after the user interface of the first applicationis zoomed out, the user can drag an icon of any second application inthe blank area to the zoomed-out user interface of the first applicationin an interaction method described above to quickly perform loginauthorization on the first application by using a login identity of theuser on the second application. In addition, in practice, the user canalso drag a target object of a specified type currently displayed in thezoomed-out user interface of the first application to an area where anyicon displayed in the blank area is located, and quickly transmit thetarget object to a second application that corresponds to the icon, toshare a file of the target object.

The target object can include any type of file that can be transmittedbetween applications, such as a text, a picture, a link, a video, or acommodity displayed in the user interface of the first application. Inpractice, backend developers of the first application can further limitin advance a type of the target object that needs to be transmittedbetween applications.

For example, in practice, backend developers of the first applicationcan specify, for the first application based on actual needs, a type ofa file that can be transmitted to another application. If the developersspecify a picture and a text as files that can be transmitted, only atext and a picture displayed in the user interface of the applicationcan respond to an operation of dragging, by the user, the target objectto an area where an icon of another application is located.

In the present example, one open interface can be preconfigured in eachsecond application that pre-establishes a login association with thefirst application. After detecting an operation of dragging, by theuser, a target object of a specified type displayed in the userinterface of the first application to an area where an icon of anysecond application displayed in the blank area is located, the operatingsystem can invoke the open interface of the second application, use thetarget object as an invocation parameter, and transmit the invocationparameter to the second application for further processing by the secondapplication.

For example, referring to FIG. 6, assume that the first application isAPP 1, the second application includes APP 2, APP 3, and APP 4, andicons of APP 2, APP 3, and APP 4 are displayed in a blank area generatedafter a user interface of APP 1 is zoomed out. Assume that the userneeds to quickly share a commodity picture displayed in the userinterface of APP 1 with APP 2. In this case, the user can drag thecommodity picture displayed in the user interface of APP 1 to an areawhere the icon of APP 2 in the blank area is located. After detectingthe operation of dragging the commodity picture to the area where theicon of APP 2 is located, the operating system can invoke the openinterface preconfigured in APP 2, use the commodity picture as aninvocation parameter, and transmit the invocation parameter to APP 2 byusing the open interface for further processing by APP 2.

It is worthwhile to note that a method that the second applicationfurther processes the transmitted target object usually depends onprocessing logic loaded in the open interface, and can include anoperation such as storing the transmitted target object locally orperforming further forwarding. In practice, backend developers of thesecond application can independently develop the open interface based onactual needs.

For example, still referring to FIG. 6, assume that APP 2 is an emailapplication, and the user needs to transmit the commodity picturedisplayed in the user interface of APP 1 to APP 2 in a form of anattachment in an email. In this case, when developing the open interfaceof APP 2, the developers of APP 2 can add execution logic of “sending afile transmitted to the APP in a form of an attachment” to a structureof the open interface. When receiving the commodity picture transmittedby APP 1, APP 2 can immediately run the execution logic to jump to anemail sending page, and add the commodity picture to the email sendingpage in a form of an attachment.

It can be seen that, in this method, a user can drag a target objectdisplayed in a zoomed-out user interface of a current application to anarea where an icon of a third-party application displayed in a blankarea is located, so that the target object can be quickly shared withthe third-party application. Therefore, the efficiency of sharing a filebetween applications can be improved.

The present application further provides an apparatus implementationthat corresponds to the previous method implementation.

Referring to FIG. 7, the present application provides an apparatus 70for an authorized login, where the apparatus is applied to a terminaldevice. Referring to FIG. 8, a hardware architecture of the terminaldevice that includes the apparatus 70 for an authorized login usuallyincludes a CPU, a memory, a nonvolatile memory, a network interface, aninternal bus, etc. For example, in software implementation, theapparatus 70 for an authorized login usually can be understood as alogical apparatus that combines software and hardware after a computerprogram loaded in the memory runs in the CPU. The apparatus 70 includesthe following: a zooming module 701, configured to zoom out a userinterface of a first application in response to a zooming operation forthe user interface of the first application; a display module 702,configured to display an icon of at least one second application that auser has logged in to in a blank area generated after the user interfaceof the first application is zoomed out, where the first applicationpre-establishes an association with the second application; atransmission module 703, configured to transmit login authorizationinformation of the second application to the first application inresponse to an operation of dragging the icon of the second applicationfrom the blank area to the zoomed-out user interface of the firstapplication, so that the first application submits the loginauthorization information of the second application to a server of thesecond application by using a server of the first application for loginauthorization verification; and a login module 704, configured toperform an authorized login to the first application in response to anotification message that is returned by the server of the secondapplication through the server of the first application, where thenotification message indicates that the login authorization informationis verified.

In the present example, the zooming module 701 is further configured to:restore the user interface of the first application to a default sizeafter successfully logging in to the first application based on thelogin authorization information of the second application.

In the present example, the transmission module 703 is furtherconfigured to: in response to an operation of dragging a target objectof a specified type displayed in the zoomed-out user interface of thefirst application to an area where any icon in the blank area islocated, transmit the target object to a second application thatcorresponds to the icon, so that the second application furtherprocesses the target object.

In the present example, the transmission module 703 is furtherconfigured to: invoke an open interface of the first application, usethe login authorization information of the second application as aninvocation parameter, and transmit the invocation parameter to the firstapplication; and invoke an open interface of the second application thatcorresponds to the icon, use the target object as an invocationparameter, and transmit the invocation parameter to the secondapplication that corresponds to the icon.

In the present example, the first application and the second applicationinclude: an APP application and a Web application.

The zooming operation includes the following: a two-finger pinch gesturefor the user interface of the first application; a predetermined triggeroperation for the user interface of the first application; and apredetermined trigger operation for a predetermined virtual button or aphysical button.

In the present example, the login authorization information includes: anapplication identifier of the second application, a user identifierallocated by the server of the second application to the user after theuser successfully logs in to the second application, and a logincertificate sent by the server of the second application after the usersuccessfully logs in to the second application.

Because an apparatus implementation basically corresponds to a methodimplementation, for related parts, references can be made to relateddescriptions in the method implementation. The previously describedapparatus implementation is merely an example. The units described asseparate parts may or may not be physically separate, and partsdisplayed as units may or may not be physical units, may be located inone position, or may be distributed on a plurality of network units.Some or all of the modules can be selected based on actual needs toachieve the objectives of the solutions in the present application. Aperson of ordinary skill in the art can understand and implement theimplementations of the present application without creative efforts.

The system, apparatus, module, or unit illustrated in the previousimplementations can be implemented by using a computer chip or anentity, or can be implemented by using a product having a certainfunction. A typical implementation device is a computer, and thecomputer can be a personal computer, a laptop computer, a cellularphone, a camera phone, a smartphone, a personal digital assistant, amedia player, a navigation device, an email receiving and sendingdevice, a game console, a tablet computer, a wearable device, or anycombination of these devices.

A person skilled in the art can easily figure out another implementationsolution of the present application after considering the presentspecification and practicing the disclosed invention here. The presentapplication is intended to cover any variations, functions, or adaptivechanges of the present application. These variations, functions, oradaptive changes comply with general principles of the presentapplication, and include common knowledge or a commonly used technicalmeans in the technical field that is not disclosed in the presentapplication. The present specification and the implementations aremerely considered as examples. The actual scope and the spirit of thepresent application are pointed out by the following claims.

It should be understood that the present application is not limited tothe accurate structures described above and shown in the accompanyingdrawings, and modifications and changes can be made without departingfrom the scope of the present application. The scope of the presentapplication is limited only by the appended claims.

The previous descriptions are merely examples of implementations of thepresent application, but are not intended to limit the presentapplication. Any modification, equivalent replacement, or improvementmade without departing from the spirit and principle of the presentapplication should fall within the protection scope of the presentapplication.

FIG. 9 is a flowchart illustrating an example of a computer-implementedmethod 900 for performing an authorized login, according to animplementation of the present disclosure. For clarity of presentation,the description that follows generally describes method 900 in thecontext of the other figures in this description. However, it will beunderstood that method 900 can be performed, for example, by any system,environment, software, and hardware, or a combination of systems,environments, software, and hardware, as appropriate. In someimplementations, various steps of method 900 can be run in parallel, incombination, in loops, or in any order.

At 905, a first user input to zoom out a first application is received.The first application is displayed on a first area of a screen of adevice. In some implementations, the first area can be a defaultdisplaying area of the screen. For example, the first area of the screencan be the entire displaying area of the screen, and the displayed firstapplication occupies the entire first area of the screen. In someimplementations, the displayed first application can occupy most of theentire displaying area of the screen in order to display one or moreindicators (such as, current time and battery life).

In some implementations, the device can be a mobile device, or apersonal computer (PC). For example, the device can be a touchscreensmartphone, a laptop, or a tablet. The operating system of the devicecan be IOS, ANDROID, WINDOWS, or another type of operating system. Thescreen can be a touchscreen or a non-touchscreen. If the screen is atouchscreen, the first user input can be a touch gesture on thetouchscreen (such as, a two-finger pinch gesture on the displayed firstapplication, and a predetermined trigger operation on the displayedfirst application). If the screen is a non-touchscreen, the first userinput can be an input through, for example, a mouse or a keyboard (suchas, a predetermined trigger operation on a virtual or physical button).

In some implementations, the first application can be an application(APP) installed on, for example, a mobile device (that is, a mobileapplication). In some implementations, the first application can be aWeb application installed on, for example, a PC. The first applicationcan be an application that a user can be authorized to directly log intousing a login identity of a third-party application. For example, thefirst application can be an application that has a small number ofusers. In response to receiving the first user input, steps 910 and 915are automatically performed.

At 910, the first application is zoomed out. The first application isdisplayed on a second area of the screen after the first application iszoomed out. The second area is smaller than the first area. For example,the second area of the screen can be part of the displaying area of thescreen, and the displayed first application after zooming out occupiesthe entire second area of the screen. From 910, method 900 proceeds to915.

At 915, at least one icon is displayed on a third area of the screen.The third area is outside the second area. For example, the third areaof the screen can be an area of the screen that is occupied by thedisplayed first application before zooming out, and is not occupied bythe displayed first application after zooming out. In other words, thethird area can be a blank area on the screen generated after thedisplayed first application is zoomed out. The at least one iconincludes an icon of a second application.

In some implementations, the second application is an APP or a Webapplication. The second application can be an application that canprovide an associated authorized login service for other applications(such as, the first application). For example, the second applicationcan be an application that has a large number of users (such as, ALIPAYand WeChat). A user has logged into the second application on the devicewhen receiving the first user input. In some implementations, the userhas not logged into the first application on the device when receivingthe first user input. In some implementations, an association betweenthe first application and the second application has beenpre-established before receiving the first user input. The associationcan be a login association between the first application and the secondapplication. The association can established by a server of the firstapplication and a server of the second application. From 915, method 900proceeds to 920.

At 920, a second user input to drag the displayed icon of the secondapplication from the third area to the second area is received. Forexample, the displayed icon of the second application is dragged to thedisplayed first application. In response to receiving the second userinput, steps 925 and 930 are automatically performed.

At 925, login authorization information of the second application istransmitted to the first application. In some implementations, the loginauthorization information includes at least one of an applicationidentifier (APP ID) of the second application, a user identifier (UID)assigned by the server of the second application to the user after theuser logged into the second application, and a login certificate (suchas, a token certificate) sent by the server of the second applicationafter the user logged into the second application. In someimplementations, the login authorization information is transmittedthrough an application program interface (API). For example, the secondapplication can preconfigure the API for data communication between thefirst application and the second application. From 925, method 900proceeds to 930.

At 930, the login authorization information is submitted by the firstapplication to the server of the second application through the serverof the first application. For example, the first application submits thelogin authorization information to the server of the first application.Then, the server of the first application submits the loginauthorization information to the server of the second application forlogin authorization verification. From 930, method 900 proceeds to 935.

At 935, logging into the first application on the device is authorizedin response to receiving a notification from the server of the secondapplication through the server of the first application. Thenotification indicates that the login authorization information isverified. For example, after receiving the login authorizationinformation, the server of the second application verifies the loginauthorization information, and transmits the notification to the serverof the first application. The server of the first application thentransmits the notification to the first application. In someimplementations, the server of the first application can set the firstapplication to a login state using, for example, user information (suchas, UID and personal information) that the user used to log into thesecond application.

In some implementations, the first application is displayed on the firstarea of the screen after successfully logging into the firstapplication. For example, the displayed first application is returned toa displaying setting used when receiving the first user input. In someimplementations, a third user input is received after successfullylogging into the first application. The third user input is to drag anobject displayed in the first application, displayed on the second areaof the screen, to the displayed icon of the second application. Inresponse to the third user input, the object is transmitted to thesecond application for further processing of the object. After 935,method 900 stops.

A third-party application can be used to perform an authorized login toa currently browsed application. Normally, when a user has successfullylogged into a second application, a login identity of the secondapplication can be used to perform an authorized login to a firstapplication. However, the user may have to perform multiple complexoperations on a login page of the first application to complete thelogin, which is not convenient for the user. The subject matterdescribed in this specification provides a simple and quick authorizedlogin method. For example, a user can zoom out of a displayed firstapplication to display an icon of the second application. Then, the usercan drag the icon of the second application to the displayed firstapplication to complete an authorized login to the first application. Indoing so, the user can perform a couple of simple and quick operationsto perform an authorized login. As a result, complexity of an authorizedlogin operation is decreased, thereby improving user experience whenperforming an authorized login.

Embodiments and the operations described in this specification can beimplemented in digital electronic circuitry, or in computer software,firmware, or hardware, including the structures disclosed in thisspecification or in combinations of one or more of them. The operationscan be implemented as operations performed by a data processingapparatus on data stored on one or more computer-readable storagedevices or received from other sources. A data processing apparatus,computer, or computing device may encompass apparatus, devices, andmachines for processing data, including by way of example a programmableprocessor, a computer, a system on a chip, or multiple ones, orcombinations, of the foregoing. The apparatus can include specialpurpose logic circuitry, for example, a central processing unit (CPU), afield programmable gate array (FPGA) or an application-specificintegrated circuit (ASIC). The apparatus can also include code thatcreates an execution environment for the computer program in question,for example, code that constitutes processor firmware, a protocol stack,a database management system, an operating system (for example anoperating system or a combination of operating systems), across-platform runtime environment, a virtual machine, or a combinationof one or more of them. The apparatus and execution environment canrealize various different computing model infrastructures, such as webservices, distributed computing and grid computing infrastructures.

A computer program (also known, for example, as a program, software,software application, software module, software unit, script, or code)can be written in any form of programming language, including compiledor interpreted languages, declarative or procedural languages, and itcan be deployed in any form, including as a stand-alone program or as amodule, component, subroutine, object, or other unit suitable for use ina computing environment. A program can be stored in a portion of a filethat holds other programs or data (for example, one or more scriptsstored in a markup language document), in a single file dedicated to theprogram in question, or in multiple coordinated files (for example,files that store one or more modules, sub-programs, or portions ofcode). A computer program can be executed on one computer or on multiplecomputers that are located at one site or distributed across multiplesites and interconnected by a communication network.

Processors for execution of a computer program include, by way ofexample, both general- and special-purpose microprocessors, and any oneor more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read-only memory ora random-access memory or both. The essential elements of a computer area processor for performing actions in accordance with instructions andone or more memory devices for storing instructions and data. Generally,a computer will also include, or be operatively coupled to receive datafrom or transfer data to, or both, one or more mass storage devices forstoring data. A computer can be embedded in another device, for example,a mobile device, a personal digital assistant (PDA), a game console, aGlobal Positioning System (GPS) receiver, or a portable storage device.Devices suitable for storing computer program instructions and datainclude non-volatile memory, media and memory devices, including, by wayof example, semiconductor memory devices, magnetic disks, andmagneto-optical disks. The processor and the memory can be supplementedby, or incorporated in, special-purpose logic circuitry.

Mobile devices can include handsets, user equipment (UE), mobiletelephones (for example, smartphones), tablets, wearable devices (forexample, smart watches and smart eyeglasses), implanted devices withinthe human body (for example, biosensors, cochlear implants), or othertypes of mobile devices. The mobile devices can communicate wirelessly(for example, using radio frequency (RF) signals) to variouscommunication networks (described below). The mobile devices can includesensors for determining characteristics of the mobile device's currentenvironment. The sensors can include cameras, microphones, proximitysensors, GPS sensors, motion sensors, accelerometers, ambient lightsensors, moisture sensors, gyroscopes, compasses, barometers,fingerprint sensors, facial recognition systems, RF sensors (forexample, Wi-Fi and cellular radios), thermal sensors, or other types ofsensors. For example, the cameras can include a forward- or rear-facingcamera with movable or fixed lenses, a flash, an image sensor, and animage processor. The camera can be a megapixel camera capable ofcapturing details for facial and/or iris recognition. The camera alongwith a data processor and authentication information stored in memory oraccessed remotely can form a facial recognition system. The facialrecognition system or one-or-more sensors, for example, microphones,motion sensors, accelerometers, GPS sensors, or RF sensors, can be usedfor user authentication.

To provide for interaction with a user, embodiments can be implementedon a computer having a display device and an input device, for example,a liquid crystal display (LCD) or organic light-emitting diode(OLED)/virtual-reality (VR)/augmented-reality (AR) display fordisplaying information to the user and a touchscreen, keyboard, and apointing device by which the user can provide input to the computer.Other kinds of devices can be used to provide for interaction with auser as well; for example, feedback provided to the user can be any formof sensory feedback, for example, visual feedback, auditory feedback, ortactile feedback; and input from the user can be received in any form,including acoustic, speech, or tactile input. In addition, a computercan interact with a user by sending documents to and receiving documentsfrom a device that is used by the user; for example, by sending webpages to a web browser on a user's client device in response to requestsreceived from the web browser.

Embodiments can be implemented using computing devices interconnected byany form or medium of wireline or wireless digital data communication(or combination thereof), for example, a communication network. Examplesof interconnected devices are a client and a server generally remotefrom each other that typically interact through a communication network.A client, for example, a mobile device, can carry out transactionsitself, with a server, or through a server, for example, performing buy,sell, pay, give, send, or loan transactions, or authorizing the same.Such transactions may be in real time such that an action and a responseare temporally proximate; for example an individual perceives the actionand the response occurring substantially simultaneously, the timedifference for a response following the individual's action is less than1 millisecond (ms) or less than 1 second (s), or the response is withoutintentional delay taking into account processing limitations of thesystem.

Examples of communication networks include a local area network (LAN), aradio access network (RAN), a metropolitan area network (MAN), and awide area network (WAN). The communication network can include all or aportion of the Internet, another communication network, or a combinationof communication networks. Information can be transmitted on thecommunication network according to various protocols and standards,including Long Term Evolution (LTE), 5G, IEEE 802, Internet Protocol(IP), or other protocols or combinations of protocols. The communicationnetwork can transmit voice, video, biometric, or authentication data, orother information between the connected computing devices.

Features described as separate implementations may be implemented, incombination, in a single implementation, while features described as asingle implementation may be implemented in multiple implementations,separately, or in any suitable sub-combination. Operations described andclaimed in a particular order should not be understood as requiring thatthe particular order, nor that all illustrated operations must beperformed (some operations can be optional). As appropriate,multitasking or parallel-processing (or a combination of multitaskingand parallel-processing) can be performed.

What is claimed is:
 1. A computer-implemented method, comprising:receiving a first user input to zoom out a first application, whereinthe first application is displayed on a first area of a screen of adevice before receiving the first user input; in response to the firstuser input: zooming out the first application, wherein the firstapplication is displayed on a second area of the screen after zoomingout the first application, and the second area is smaller than the firstarea; and displaying at least one icon on a third area of the screen,wherein the third area is outside the second area, the at least one iconincludes an icon of a second application, and a user has logged into thesecond application on the device; receiving a second user input to dragthe displayed icon of the second application from the third area to thesecond area; in response to the second user input: transmitting loginauthorization information of the second application to the firstapplication; and submitting, by the first application, the loginauthorization information to a server of the second application througha server of the first application; and authorizing logging into thefirst application on the device in response to receiving a notificationfrom the server of the second application through the server of thefirst application, wherein the notification indicates that the loginauthorization information is verified.
 2. The computer-implementedmethod of claim 1, wherein the first application is not logged into bythe user on the device when receiving the first user input, and theserver of the second application is used for login authorizationverification.
 3. The computer-implemented method of claim 1, wherein anassociation between the first application and the second application hasbeen pre-established before receiving the first user input.
 4. Thecomputer-implemented method of claim 1, wherein the login authorizationinformation includes at least one of an application identifier of thesecond application, a user identifier assigned by the server of thesecond application to the user after the user logged into the secondapplication, and a login certificate sent by the server of the secondapplication after the user logged into the second application.
 5. Thecomputer-implemented method of claim 1, further comprising displayingthe first application on the first area of the screen after successfullylogging into the first application.
 6. The computer-implemented methodof claim 1, wherein the first application and the second applicationinclude a mobile application and a Web application, and the first userinput includes a two-finger pinch gesture on the displayed firstapplication, a predetermined trigger operation on the displayed firstapplication, and a predetermined trigger operation on a virtual orphysical button.
 7. The computer-implemented method of claim 1, furthercomprising: receiving a third user input to drag an object displayed inthe first application, displayed on the second area of the screen, tothe displayed icon of the second application; and in response to thethird user input, transmitting the object to the second application forfurther processing of the object.
 8. A non-transitory, computer-readablemedium storing one or more instructions executable by a computer systemto perform operations comprising: receiving a first user input to zoomout a first application, wherein the first application is displayed on afirst area of a screen of a device before receiving the first userinput; in response to the first user input: zooming out the firstapplication, wherein the first application is displayed on a second areaof the screen after zooming out the first application, and the secondarea is smaller than the first area; and displaying at least one icon ona third area of the screen, wherein the third area is outside the secondarea, the at least one icon includes an icon of a second application,and a user has logged into the second application on the device;receiving a second user input to drag the displayed icon of the secondapplication from the third area to the second area; in response to thesecond user input: transmitting login authorization information of thesecond application to the first application; and submitting, by thefirst application, the login authorization information to a server ofthe second application through a server of the first application; andauthorizing logging into the first application on the device in responseto receiving a notification from the server of the second applicationthrough the server of the first application, wherein the notificationindicates that the login authorization information is verified.
 9. Thenon-transitory, computer-readable medium of claim 8, wherein the firstapplication is not logged into by the user on the device when receivingthe first user input, and the server of the second application is usedfor login authorization verification.
 10. The non-transitory,computer-readable medium of claim 8, wherein an association between thefirst application and the second application has been pre-establishedbefore receiving the first user input.
 11. The non-transitory,computer-readable medium of claim 8, wherein the login authorizationinformation includes at least one of an application identifier of thesecond application, a user identifier assigned by the server of thesecond application to the user after the user logged into the secondapplication, and a login certificate sent by the server of the secondapplication after the user logged into the second application.
 12. Thenon-transitory, computer-readable medium of claim 8, the operationsfurther comprising displaying the first application on the first area ofthe screen after successfully logging into the first application. 13.The non-transitory, computer-readable medium of claim 8, wherein thefirst application and the second application include a mobileapplication and a Web application, and the first user input includes atwo-finger pinch gesture on the displayed first application, apredetermined trigger operation on the displayed first application, anda predetermined trigger operation on a virtual or physical button. 14.The non-transitory, computer-readable medium of claim 8, the operationsfurther comprising: receiving a third user input to drag an objectdisplayed in the first application, displayed on the second area of thescreen, to the displayed icon of the second application; and in responseto the third user input, transmitting the object to the secondapplication for further processing of the object.
 15. Acomputer-implemented system, comprising: one or more computers; and oneor more computer memory devices interoperably coupled with the one ormore computers and having tangible, non-transitory, machine-readablemedia storing one or more instructions that, when executed by the one ormore computers, perform one or more operations comprising: receiving afirst user input to zoom out a first application, wherein the firstapplication is displayed on a first area of a screen of a device beforereceiving the first user input; in response to the first user input:zooming out the first application, wherein the first application isdisplayed on a second area of the screen after zooming out the firstapplication, and the second area is smaller than the first area; anddisplaying at least one icon on a third area of the screen, wherein thethird area is outside the second area, the at least one icon includes anicon of a second application, and a user has logged into the secondapplication on the device; receiving a second user input to drag thedisplayed icon of the second application from the third area to thesecond area; in response to the second user input: transmitting loginauthorization information of the second application to the firstapplication; and submitting, by the first application, the loginauthorization information to a server of the second application througha server of the first application; and authorizing logging into thefirst application on the device in response to receiving a notificationfrom the server of the second application through the server of thefirst application, wherein the notification indicates that the loginauthorization information is verified.
 16. The system of claim 15,wherein the first application is not logged into by the user on thedevice when receiving the first user input, and the server of the secondapplication is used for login authorization verification.
 17. The systemof claim 15, wherein an association between the first application andthe second application has been pre-established before receiving thefirst user input.
 18. The system of claim 15, wherein the loginauthorization information includes at least one of an applicationidentifier of the second application, a user identifier assigned by theserver of the second application to the user after the user logged intothe second application, and a login certificate sent by the server ofthe second application after the user logged into the secondapplication.
 19. The system of claim 15, the operations furthercomprising displaying the first application on the first area of thescreen after successfully logging into the first application.
 20. Thesystem of claim 15, wherein the first application and the secondapplication include a mobile application and a Web application, and thefirst user input includes a two-finger pinch gesture on the displayedfirst application, a predetermined trigger operation on the displayedfirst application, and a predetermined trigger operation on a virtual orphysical button.